home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Language/OS - Multiplatform Resource Library
/
LANGUAGE OS.iso
/
cpp_libs
/
sos3-2_r.lha
/
README.install.SOS3-2
< prev
Wrap
Text File
|
1992-02-13
|
8KB
|
190 lines
(1) Introduction
----------------
This file describes the installation of SOS version 3-2.
SOS is the STONE object management system developed by Forschungszentrum
Informatik (FZI) as a contribution to the STONE project. This project
(supported by grant no. ITS8902A7 from the BMFT) aims at the development of
a software engineering environment for education purposes and is carried out
as a joint project of nine german universities and research institutions.
An essential feature of STONE is that the object oriented paradigm is pursued
consequently as a key concept. SOS is the common persistent object store for
all tools within the STONE environment.
Since SOS is a prototype you have to be aware of possible bugs. On sending a
short report we will try hard to fix them but we can not give guarantees of any
kind.
More specifically:
FZI DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL FZI BE
LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Besides bug reports we are strongly interested in all experiences our users
make with SOS (e.g. sufficiency of data model, performance, ...) and in our
users' application areas and the applications as well.
Please mail to: Forschungszentrum Informatik (FZI)
STONE Projekt
Haid-und-Neu-Strasse 10-14
D-7500 Karlsruhe 1
Germany
or email to: stone@fzi.de
Phone: ++49-721-9654-601
Fax: ++49-721-9654-609
Teletex: 721 190 fziKA
On sending a short note (preferably via email to stone@fzi.de) we'll keep
you informed about SOS enhancements, new versions, etc.
(2) System Requirements
-----------------------
The installation has been tested for Sun3, Sun4 running os4 and the C++
compilers GNU g++ (versions 1.37.0 up to 1.39.1) and AT&T C++ version 2.0/2.1.
Some of the graphical tools comprised in the SOS version are based on X-windows
(X11R4).
Porting to other machines shouldn't make problems if there is a GNU g++
compiler available.
An SOS version installed using the compilation switch settings as delivered
requires about 40 MByte disk space.
(3) Starting the Installation
-----------------------------
Your local directory should now contain six files:
README.install.SOS3-2: this file
README.changes.SOS3-2: contains differences to the last delivered version.
README.SOS3-2 : short description of the SOS version 3-2.
LICENCE : licence conditions for the SOS version 3-2.
INSTALL.SOS3-2 : UNIX script performing most of the installation.
SOS3-2.tar.Z : compressed tar file containing the SOS version 3-2.
Before the actual installation is started, you should move at least the last
two files (or all six files) to the directory where you want to install SOS.
Now, change directory to the directory containing INSTALL.SOS3-2 and SOS3-2.tar.Z.
SOS will be installed in this directory.
Most parts of the installation are performed by the script INSTALL.SOS3-2. The
installation consists of three phases:
- First, INSTALL.SOS3-2 unpacks the SOS version and installs it in your local
directory tree.
- Afterwards, you perform any adaptions to your local environment not done in
the first phase.
- Finally, INSTALL.SOS3-2 triggers a bootstrap of the SOS version.
Start by typing:
INSTALL.SOS3-2
This will unpack SOS3-2.tar.Z and afterwards ask you for the C++ compiler to be
used (see also below). For the GNU compiler type 'y' or 'Y', for the AT&T
compiler type 'n' or 'N'.
INSTALL.SOS3-2 will now change some paths to integrate the SOS version into your
directory tree.
(4) Customization at Your Site
------------------------------
Some adaptions are difficult to perform automatically. Therefore, you have to
finish the customization by yourself. You might consider to refer to the SOS
Users Guide contained in SOS3-2/doc/system for an explanation of some of the
terms used in the sequel.
We had some problems with the compilation driver CC (version 1.7.3.1)
included in the AT&T C++ 2.0 distribution. Therefore, you might consider to
adapt your CC script when compiling with the AT&T compilers as follows (a CC
script with the following changes is contained in SOS3-2/bin):
- Changing line 219 from
$cfrontC +L +f$A $O <$TEMPDIR/cpptmp >$TEMPDIR/$B$ISUF
to
$cfrontC +L +f$A $O <$TEMPDIR/cpptmp \
| egrep -v '^#line.*\.h\"' \
> $TEMPDIR/$B$ISUF
removes #line comments from the output of cfront. These comments caused a
bus error in subsequent cpp runs at our installation.
- Changing lines 363, 365 from
echo "$ccC $P $NLO $X" 1>&2
(cd $TEMPDIR; $ccC $P $NLO $X)
to
echo "$ccC $P $NLO $OF $X" 1>&2
(cd $TEMPDIR; $ccC $P $NLO $OF $X)
handles the '-o' option in the NOLOAD case.
- When using AT&T 2.0 (and NOT 2.1) then you must transform line 38 in
SOS3-2/src/psm/psm.c to "#include <sys/time.h>", i.e. you must delete "//".
The SOS makefile is based on macros defined in SOS3-2/commands.mk. These
macros define in particular the compilers and the compilation options used
during the generation of the SOS version. You might want to customize these
macros according to your local installation.
In the header of the SOS makefile SOS3-2/Makefile you will find the four
macros ECHOXX, LDXX, CRTXX, and LIBSXX. These macros define default options for
the incremental loading facility of SOS. As described in the Users Guide, these
defaults can be overridden at runtime of an SOS application by defining an
environment variable. Incremental loading is only operable if the SOS version
is installed with the GNU compiler (see above). Otherwise, the macros are not
used and may therefore define arbitrary values.
ECHOXX ... set this to TRUE (FALSE), if the names of incrementally loaded
object files are (not) to be echoed on stderr.
LDXX ... the pathname of the link editor distributed with the GNU
C++ compiler
CRTXX ... the pathname of the object module containing startup code for the
incrementally loaded code
LIBSXX ... linker options for standard libraries to be appended to each
link command
Furthermore, the locking mechanism used by the persistent storage manager to
implement process synchronization can be chosen via the macro USE_FCNTL. This
macro is contained in the header of the Makefile, too.
If USE_FCNTL is defined by "-DLOCKD_CORRECT", locks will be claimed using
the Unix system call 'fcntl', otherwise using 'flock'.
In the first case, locks will be respected network wide, in the second case
only among the processes running on a single host.
SOS is by default n o t generated using network wide locks. The primary
reason for this is an error in the Sun Os 4.1.1 implementation of the lock
daemon required for network wide locks. This error occasionally caused a halt
of the addressed file server. The error ceased to occur after the installation
of an OS patch obtained from Sun (patch no. 100075-07).
(5) Completing the Installation
-------------------------------
After completing the customization, the final phase of the SOS installation
is started by typing
INSTALL.SOS3-2 -boot
This triggers the boot process for the SOS version. It will take some time
until the system is built up completely. During the bootstrap the schema
compiler as well as some tools and demonstration programs that are comprised in
the delivered software will be generated.
Finally, you are asked whether the object files created during installation
shall be kept or removed. If no error occured, most object files are not
necessary any further since they are bound to libraries or executables,
respectively. In this case you can savely answer the question with 'y' or 'Y'.
Otherwise, type 'n' or 'N' and the object files are kept.
The same holds for the installation files INSTALL.SOS3-2, and SOS3-2.tar.Z which are
removed if you answer the corresponding question 'remove installation files?'
with 'y' or 'Y' and kept if the answer is 'n' or 'N'.
This finishes the installation of your SOS version.
Have fun with SOS.